Triaging Bugs

What is a bug and why does it matter?

A bug is an issue that prevents the product from behaving or functioning as designed. This is different from the product behaving in a way that the users don't expect it to. Let’s take an example: In the Sworkit app's exercise library each exercise has a video demo in a loop with instructions to read. When the same exercise is part of an active workout, it has audio instructions. It may be designed intentionally this way since exercisers browsing the exercise library can read the instructions while exercises working out cannot. If an exerciser reports an issue that audio is not playing on the exercise details page, I recommend understanding the user's reasoning.

A common misconception is new functionality development trumps bug fixing. This is not the case since Product Managers evaluate the bugs on a case by case basis to determine whether the bug needs to be fixed now vs. later. The first step is confirming whether the reported issue is a bug or a mismatch in user expectations. If the reported issue is a bug, then determine whether it's reproducible every time. Let’s take an example: Imagine using any messaging app and you are unable to include an emoji in the text. When you tap on the emoji it shows as selected but doesn’t appear in the text you typed. This issue is reproducible every time an emoji is selected regardless of whether the user tries to add it at the beginning, mid-sentence or end of the sentence.

We will spend the next few minutes understanding how does an issue's severity determines the priority to fix the bug.